You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Fixes#38
- New Dash endpoint does *not* return work positions in correct order,
so methods that were looking up elements by type instead of accessing
via Table-of-Contents (which preserves order in arrays), were getting
entities back in the correct order (was actually completely reversed
for some endpoints!)
- Fix is to switch to always looking up entities by ToC, for both API
response types, to make sure work position order is always preserved
- This affects both regular JSON Resume and vCard export, although I
believe the issue filed was in reference to vCard specifically
Copy file name to clipboardexpand all lines: README.md
+11
Original file line number
Diff line number
Diff line change
@@ -73,6 +73,7 @@ When in doubt, refresh the profile page before using this tool.
73
73
## Updates:
74
74
Date | Release | Notes
75
75
--- | --- | ---
76
+
12/19/2020 | 2.1.1 | Fix: Ordering of work history with new API endpoint ([#38](https://github.com/joshuatz/linkedin-to-jsonresume/issues/38))
76
77
12/7/2020 | 2.1.0 | Fix: Issue with multilingual profile, when exporting your own profile with a different locale than your profile's default. ([#37](https://github.com/joshuatz/linkedin-to-jsonresume/pull/37))
77
78
11/12/2020 | 2.0.0 | Support for multiple schema versions ✨ ([#34](https://github.com/joshuatz/linkedin-to-jsonresume/pull/34))
If you do want to find the actual injected code of the extension in Chrome dev tools, you should be able to find it under `Sources -> Content Scripts -> top -> JSON Resume Exporter -> {main.js}`
138
139
140
+
#### Debugging Snippets
141
+
Helpful snippets (subject to change; these rely heavily on internals):
142
+
143
+
```js
144
+
// Get main profileDB (after running extension)
145
+
var profileRes =awaitli2JrInstance.getParsedProfile();
146
+
var profileDb =awaitli2JrInstance.internals.buildDbFromLiSchema(profileRes.liResponse);
* Get all elements that match type. Should usually just be one
117
+
* Get all elements that match type.
118
+
* WARNING: Since this gets elements directly by simply iterating through all results, not via ToC, order of entities returned is simply whatever order LI provides them in the response. Not guaranteed to be in order! Use a ToC approach if you need ordered results.
118
119
* @param {string | string[]} typeStr - Type, e.g. `$com.linkedin...`
0 commit comments