hazaar/framework
1
0
Fork 0
Code Issues 14 Pull requests 1 Projects Releases Packages 1 Wiki Activity Actions

CDNJS: Re-check library info when a specific version is requested #119

New issue
Closed
opened 2018-02-06 02:25:25 +00:00 by jamie · 2 comments
jamie commented 2018-02-06 02:25:25 +00:00 (Migrated from git.hazaar.io)
Copy link

Currently, if a specific version is requested and it is not known in the last available library info, an exception is thrown. The problem is if the library info was created, then some time later a new version was added, trying to use this version will throw the exception because this version is not known in the stored library info and this info is never updated because talking to the CDNJS API is slow.

What I think we can do to fix half of this problem is, if a specific version is requested and that version is not found in the current library info, download the latest library info and check again. This will trigger an update and setting an explicit library version will work. If the version is still not found when that happens, THEN throw the exception.

The one thing this will not help with is using the automatic library version. But this can just be a known caveat.

Currently, if a specific version is requested and it is not known in the last available library info, an exception is thrown. The problem is if the library info was created, then some time later a new version was added, trying to use this version will throw the exception because this version is not known in the stored library info and this info is never updated because talking to the CDNJS API is slow. What I think we can do to fix half of this problem is, if a specific version is requested and that version is not found in the current library info, download the latest library info and check again. This will trigger an update and setting an explicit library version will work. If the version is still not found when that happens, THEN throw the exception. The one thing this will not help with is using the automatic library version. But this can just be a known caveat.
jamie commented 2018-02-06 04:39:44 +00:00 (Migrated from git.hazaar.io)
Copy link

closed via commit 6c7c968cf9

closed via commit 6c7c968cf931209e5ed23cd3d7ce8dd236847729
jamie commented 2018-06-29 02:24:26 +00:00 (Migrated from git.hazaar.io)
Copy link

changed milestone to %4

changed milestone to %4
jamie self-assigned this 2025-09-04 01:15:46 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
586-gitlab-ci-migration
297-feature-router-security
develop
No results found.
Labels
Clear labels   
bug

   
confirmed

   
critical

   
discussion

   
documentation

   
Doing

   
enhancement

   
experiment

Experimental Feature

  
suggestion

   
support

   
Testing

   
To Do
No labels
bug
confirmed
critical
discussion
documentation
Doing
enhancement
experiment
suggestion
support
Testing
To Do
Milestone
Clear milestone
No items
No milestone
Release 2.4
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
jamie
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: hazaar/framework#119
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?