Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

See the following notebook

# Databricks notebook source

table_name = "old.things"  # Migrated table according to the migration index

# COMMAND ----------

spark.table(table_name)

# COMMAND ----------

table_name = "not_migrated.table"  # NOT a migrated table according to the migration index

The spark.table(table_name) is reading a migrated table hence we expect a deprecation warning to be given that says to use the migrated table. However, the linter does not yield such a warning because it uses the table_name from the lowest cell.

Expected Behavior

A cell should only include the context from itself cell, the cells above and possible context from %run references

Steps To Reproduce

No response

Cloud

Azure

Operating System

macOS

Version

latest via Databricks CLI

Relevant log output