9ff6dcbe0a
[JS FIR] Add a test for generic interface inheritance
...
^KT-65216
2024-02-13 12:19:29 +00:00
3dd4a0d868
[JS FIR] Add JS_NAME_CLASH tests for constructors
...
^KT-64867 Related
2024-01-23 10:30:10 +00:00
5da4d31d37
[JS FIR] Rework JS_NAME_CLASH diagnostic for constructors
...
- Fix a false positive JS_NAME_CLASH report on constructors
from different classes but with the same JsName.
- Allow the same JsName for class constructors and other top-level
declarations. This behavior differs from K1, but it is correct
since there is no real name clash in the generated JS code.
^KT-64867 Fixed
2024-01-23 10:30:10 +00:00
fc584b7c33
[JS FIR] Add non-ASCII JsName tests
...
^KT-64463 Related
2024-01-23 10:00:18 +00:00
4609b11102
[JS FIR] Add JsName clash test
...
^KT-64364
2024-01-02 10:15:02 +00:00
eb790732fd
[K/JS] Enable identifiers escaping by default in 2.1 version ^KT-31799 Fixed
2023-12-20 16:39:19 +00:00
b1465fbfb8
[JS FIR] Enable warnings and infos for JS FIR tests
2023-11-27 14:31:31 +00:00
8e4a6759a4
[FIR] Fix Disappeared INVALID_CHARACTERS
...
^KT-59996 Fixed
2023-10-31 22:04:06 +00:00
f07028959d
[FIR JS] Add more tests for JS_NAME_CLASH diagnostic
...
^KT-61862 Related
2023-09-13 10:54:57 +00:00
ea9e2eb41a
[FIR JS] Add more tests for JS_NAME_CLASH and JS_FAKE_NAME_CLASH
...
^KT-59425 Related
^KT-59370 Related
2023-09-08 09:55:25 +00:00
6bb939c6cb
[FIR JS] Support JS_NAME_CLASH and JS_FAKE_NAME_CLASH diagnostics
...
^KT-59425 Fixed
^KT-59370 Fixed
2023-09-08 09:55:25 +00:00
89c3781c8e
[JS FIR] Support NAME_CONTAINS_ILLEGAL_CHARS diagnostic
...
^KT-59392 Fixed
2023-07-21 13:54:34 +00:00
37c8ec1e51
[JS FIR] Support JS_BUILTIN_NAME_CLASH diagnostic
...
^KT-59391 Fixed
2023-07-21 13:54:34 +00:00
5817155616
[FIR JS] Implement FirJsNameChecker
2023-01-09 08:57:12 +00:00
73c89a5d9d
[FIR JS] Prepare the test data for FIR
2023-01-09 08:57:08 +00:00
918a91dbdf
Escape special names with backticks in test data
...
#KT-51248
2022-02-10 21:20:47 +00:00
979e9f94ef
feat(Escaped Identifiers): add ability to use any symbol wrapped in back ticks.
2021-10-29 17:55:59 +00:00
71ffaa2d97
[TEST] Migrate AbstractDiagnosticsTestWithJsStdLib to new test runners
2020-12-16 19:52:29 +03:00
d1e1e274d9
Render property accessor annotations in .txt test data
...
If property accessor rendering is disabled in a test, render annotations
on accessors as use-site-targeted, as was done with
`@setparam:`-annotations. Otherwise they were lost
2018-10-24 18:17:12 +02:00
fc87043cb3
Merge use-site targeted annotations into corresponding Annotations
...
Add PropertyDescriptor.backingField/delegateField to store annotations
on the field directly in an otherwise almost empty descriptor instance,
instead of storing them with use-sites in the corresponding property
descriptor. Instead of AnnotationWithTarget, create AnnotationDescriptor
instances in AnnotationSplitter. Change DescriptorRenderer to render
annotations on "related" declarations when needed, with the explicit
use-site target if applicable.
Most changes in diagnostic test data are related to the fact that
annotations which are known to have an incompatible use-site to the
declaration they're applied at (such as `@param:`-annotation on a
function), are now not loaded at all. It's fine because the code is
erroneous, so it doesn't really matter how do we load annotations with
invalid targets (some of this logic is also changed freely in subsequent
commits). Some changes are also explained by the fact that for example
an annotation on the property which is only applicable to FIELD is now
rendered with an explicit use-site target `@field:`, regardless of
whether it did have that use-site target syntactically or not.
Basically, after this change there's no point in calling
Annotations.getUseSiteTargetedAnnotations/getAllAnnotations anymore
because it's easier and more intuitive to just use Annotations of the
corresponding descriptor -- the backing / delegate field (introduced in
this commit) or the extension receiver / setter parameter (related
behavior was fixed in previous commits). Usages of
use-site-target-related methods will be refactored out in subsequent
commits
2018-09-06 19:13:11 +03:00
e76debb12b
Report UNUSED_PARAMETER in setter #KT-21129 Fixed
2018-05-04 18:04:57 +03:00
6adb62f3a2
JS: prohibit declaration names that clash with JS builtin functions
...
See KT-18095, KT-17475, KT-18105, KT-5259
2017-10-23 17:19:52 +03:00
ca014468ee
JS: improve name clash checker to handle complicated cases
...
See KT-18010
2017-09-26 13:56:19 +03:00
28c9d274ec
JS: prohibit illegal chars on dynamic call site
...
See KT-19540
2017-09-04 15:35:00 +03:00
472959aca1
Improve rendering of modifiers in DescriptorRenderer
...
* Use bold font to render all modifiers
* Render 'external' according to the style guide, right after modality
2017-08-25 15:35:05 +03:00
9375a1d984
Prohibit illegal identifiers in packages in JS BE
...
See KT-18032
2017-05-29 15:37:30 +03:00
f4ef98c327
Remove test for named native
2017-01-30 19:21:41 +03:00
06e8f7b328
JS: don't report error when FAKE function overrides external function with optional parameters. Report only when it overrides at least two such functions. See KT-15961
2017-01-30 17:26:07 +03:00
900adcf29b
JS: prohibit stable (public) names with non-identifier chars. Rewrite unstable (private) names with non-identifier chars. See KT-4160
2016-12-30 16:21:18 +03:00
ed7ac7cea9
JS: do not report declaration clash when common redeclaration diagnostic applies. See KT-14577
2016-12-29 16:00:36 +03:00
fff1af4ff6
JS: allow to inherit external classes with overloaded functions in case we don't override them (see KT-13910).
2016-12-09 15:13:09 +03:00
68412ae94f
JS: replace all usages of @native annotation with external modifier, in tests, stdlib, etc
2016-12-08 15:41:39 +03:00
71ef8c4f89
JS: fix exception in JS front-end when checking JsName that was resolved with errors
2016-11-11 11:11:19 +03:00
f22a507e39
JS: add test to prove that #KT-5051 is no more reproducible
2016-10-20 12:16:30 +03:00
c814a9d1d2
KT-2752: fix support of typealiases
2016-10-08 19:25:52 +03:00
6f7e7d8504
KT-2752: fixes after code review
2016-10-08 19:25:49 +03:00
4e2b1d68cf
KT-2752: deprecate parameter of @native annotation, prohibit simultaneous usage of parameterized @native and @JsName
2016-10-08 19:25:42 +03:00
49022fd5bc
KT-2752: move some diagnostics from entire declarations to their headers
2016-10-08 19:25:41 +03:00
681a428473
KT-2752: prohibit JSName on extension properties
2016-10-08 19:25:36 +03:00
1dcb037aee
KT-2752: remove diagnostic that reports about overridden method having several names from different sources. Generate proxies instead. Fix reporting name clash when two distinct fake overrides require same name.
2016-10-08 19:25:35 +03:00
c5087779e4
KT-2752: add diagnostics that reports about conflicting overridden declarations
2016-10-08 19:25:34 +03:00
16c172f053
KT-2752: add diagnostic that reports about applying JsName on overridden declarations
2016-10-08 19:25:33 +03:00
725d13b72e
KT-2752: fix JsName with explicit use target. Add some tests for JsName with use targets
2016-10-08 19:25:33 +03:00
be0013d9f2
KT-2752: declare properties as a pair of functions when accessors are marked with @JsName
2016-10-08 19:25:32 +03:00
6e1a0901ac
KT-2752: add checkers for inconsistent usage of JsName
2016-10-08 19:25:31 +03:00
50dd1e31c3
KT-2752: move tests, that check whether there's no name clash, to JS backend tests
2016-10-08 19:25:29 +03:00
5ce158f297
KT-2752: add basic tests for JsName
2016-10-08 19:25:28 +03:00
8738458c34
KT-2752: fix name clash diagnostic for case of extension property. Add more tests for the diagnostic
2016-10-08 19:25:27 +03:00
8f829557c8
KT-2752: add diagnostic that checks whether Kotlin declarations produce conflicting names in generated JS
2016-10-08 19:25:26 +03:00
Alexander Korepanov