v0.0.4
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
0.0.4 - 2025-01-14
Fixed
- On Hover rendered Macro calls parametes as
[object object]
instead of the actual string value e.g
reg = <536870912 DT_SIZE_K([object object])>; -> issue
reg = <536870912 DT_SIZE_K(448)>; -> fix
0.0.3 - 2025-01-13
Added
- Formating of comments
- Code action to add missing properties
Fixed
- Formating of includes statment in files that where included inside a DTC node
0.0.2 - 2025-01-10
Added
- Support for
devicetree.cwd
in the setting. This can be used to allow relative paths in:devicetree.defaultIncludePaths
devicetree.defaultZephyrBindings
- Support for
cwd
in each context. If this is missingdevicetree.cwd
will be used as falback. This can be used to allow relative paths in:includePaths
zephyrBindings
dtsFile
ctxName
to the context settings. This can be a string or a number.- Extended
preferredContext
to support linking toctxName
. This can be a string or a number. devicetree.autoChangeContext
. If true the LSP will auto change the active context for actions. Defaults to true.devicetree.allowAdhocContexts
If true the LSP will create ad hoc context for when.dts
file is opned and not in anydevicetree.contexts
. Defaults to true. If not context is avalable for a devicetree file a warning.- Formating
include
in document - Formating now support confiuration of tab vs spaces and spaces size
Fixed
- Parsing files with
include
that is not in the root of the document e.g.
/dts-v1/;
#include "nrf5340_cpuapp_common.dtsi" // -> OK
/ {
model = "Nordic NRF5340 DK NRF5340 Application";
compatible = "nordic,nrf5340-dk-nrf5340-cpuapp";
chosen {
#include "nrf5340_cpuapp_common.dtsi" // -> ISSUE Fixed
};
};
0.0.1 - 2025-01-07
Added
- First release