[Bug] chronological_record_meta
in config.yml
can not be specified another custom meta.
#56
Closed
1 of 3 tasks
Labels
bug
Something isn't working
What version of Cosma are you using?
CLI 2.0.0
On which operating system(s) did you observe the bug?
What version of the operating system are you on?
Windows 10
Actions leading to the bug
npm install @graphlab-fr/cosma -g
, version 2.0.2cosma c
add a configure file and write itcosma m
cosmoscope.html
in BrowserBug description
Since migration, all my markdown files have the same creation date on Windows. Fortunately, their front-matter has a
date
metadate field that records the actural creation date of the file. Its format is like 2023-07-10 23:16:32.I refered the user manual, which states that
chronological_record_meta
in cosma configuration file can be set to another metadata field declared in record_metas.Here is an example YAML configuration:
However, it didn't work as expected. After running
cosma m
, thechronological_record_meta
reverted back to the default value 'created' .I questioned whether the format of
date
was incorrect, but I have tried 2023-07-10, 20230710231632 and 1650257016(timestamp), none of which worked. Did I make any mistakes?Additional information
The html page is displayed as below as I click 'Mode chronologique':
![image](https://private-user-images.githubusercontent.com/61202052/259182345-45c76fce-212e-42ec-a9b8-51cd9030dae8.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjA3MDk5MDIsIm5iZiI6MTcyMDcwOTYwMiwicGF0aCI6Ii82MTIwMjA1Mi8yNTkxODIzNDUtNDVjNzZmY2UtMjEyZS00MmVjLWE5YjgtNTFjZDkwMzBkYWU4LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzExVDE0NTMyMlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTA2OTcwMDJhMWY4Y2IzYjAyMzFlNzJhZTRjMjdmNmEwNzQzYTk3NjE2NmM1NmEzNjBjNzc2N2Y3ZTRhMTJhNjMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.hhQmHmbxZBXDBEfb9akyrzvuT75CpDHmCT5IVPLydPM)
The text was updated successfully, but these errors were encountered: